A security issue was found in Composer before versions 1.10.22 and 2.0.13. URLs for Mercurial repositories in the root composer.json and package source download URLs are not sanitized correctly. Specifically crafted URL values allow code to be executed in the HgDriver if hg/Mercurial is installed on the system. The impact to Composer users directly is limited as the composer.json file is typically under their own control and source download URLs can only be supplied by third party Composer repositories they explicitly trust to download and execute source code from, e.g. Composer plugins. The main impact is to services passing user input to Composer, including Packagist.org and Private Packagist. This allowed users to trigger remote code execution.
A security issue was found in Composer before versions 1.10.22 and 2.0.13. URLs for Mercurial repositories in the root composer.json and package source download URLs are not sanitized correctly. Specifically crafted URL values allow code to be executed in the HgDriver if hg/Mercurial is installed on the system. The impact to Composer users directly is limited as the composer.json file is typically under their own control and source download URLs can only be supplied by third party Composer repositories they explicitly trust to download and execute source code from, e.g. Composer plugins. The main impact is to services passing user input to Composer, including Packagist.org and Private Packagist. This allowed users to trigger remote code execution.
https://github.com/composer/composer/security/advisories/GHSA-h5h8-pc6h-jvvx https://github.com/composer/composer/commit/083b73515d1d72bc61c6374440b3f8a37531f8cf https://github.com/composer/composer/commit/332c46af8bebdead80a2601350dff7af0ac1f490
Vulmon